Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
Christopher Liam Ivey
Participant
Christopher Liam Ivey
Participant
Activity
‎Mar 24, 2021
09:33 AM
I'm glad to hear that. I'll try downloading the update and see how it works for me.
... View more
‎Mar 12, 2020
03:23 PM
I'm trying to use tilt-shift blur on a canvas about 5400x3000 pixels. I have the latest build of Photoshop, (21.0.1) and a kick-ass Alienware computer with lots of RAM. The damn thing freezes and crashes repeatedly. Yes, I have increased the cache level above 4. Yes, I have tried toggling GPU acceleration (on and off). Yes, I have reduced the bit depth to 8-bits. I'm so sick of this program dying every time I look at it cross-eyed. Any suggestions as to how to get this feature to work? I am profoundly unimpressed at this point because this is the third feature that's hung up in the past week - in a clean new install on the most expensive laptop our IT team could find - configured by professionals.
... View more
‎Jan 20, 2020
01:41 PM
I'll give that a try. This is curious, since the last build was performing fine.
... View more
‎Jan 20, 2020
11:44 AM
4 Upvotes
Something curious: I updated to Photoshop v21.01, and now it's curiously slow resizing images.
Simply resizing a 4K (3840) image to 1K(1920) using basic bicubic resampling can take 10 seconds or more - Much more if I use a more expensize algorithm live preserve details 2 or have a lot of layers in my image.
What gives? I have an absolute powerhouse computer and this action was almost instantaneous (except for very large files) in the last build of Photoshop. What are you guys doing now during a resize?
{Thread renamed by moderator}
... View more
‎Dec 12, 2019
11:37 AM
I did that before posting this enquiry. Lighting effects just renders a black viewport.
... View more
‎Dec 12, 2019
10:09 AM
I can't get lighting effects to render anything at all in Photoshop 21.0.1. Generally speaking, they just produce a black screen, (unless I turn the ambient light values up to max). I have performance preferences set to use the graphics processor, and I'm using an Nvidia 2060 with the latest drivers. I haven't found any useful information in other posts.
Does anyone have any ideas as to what I can do to get these effects to actually render? This worked for me in the last release.
{Thread renamed by moderator}
... View more
‎Oct 22, 2019
10:23 AM
1 Upvote
Oh, it's definite crap I'm dealing with. CMS templates have become a bloated, horrible mess, with mutiple layers of foundations, each overriding the CMS of the last. So much duplication.
... View more
‎Oct 22, 2019
10:10 AM
Thanks everyone for your replies, even if this remains unresolved. I can't see any button to mark this thread as closed, but from my perspective this question is answered.
... View more
‎Oct 22, 2019
10:08 AM
That's not my choice, so this is not a helpful reply. I have to work with what I'm given and don't have time to rebuild an entire template system written by heaven only knows who. I just have to make it work. For now, I'm using a trial of Sublime Text which seems a little nicer than Notepad ++. I'd love to use Dreamweaver, since I'm paying for it, but if resolving this isn't simply a matter of changing a setting or making a quick fix, I can't spend any more time on this issue.
... View more
‎Oct 22, 2019
08:48 AM
The code is from a commercial template. It's bulky, but it renders just fine, and very quickly in any browser you choose to test with, with no errors showing in the property inspector. I am editing the code directly - opening only the .css file. Searching within the code is really slow, and edits are impossibly slow. I'm going to try to download Sublime and Visual Studio Code and give those a whirl.
... View more
‎Oct 22, 2019
07:43 AM
I'm trying to edit some big .css files, (about 400 KB). I only have one file open. If I try to edit text, each keystroke takes between 15 and 30 seconds to register. Does anyone have any suggestions? It's a new, clean install, and seems to work fine with small files.
... View more
‎Apr 12, 2019
02:25 PM
Thanks everyone for your help. I found out that: 1) Illustrator can't handle very large files in .jpeg format, but will open even larger files if you save as .psb or .tiff. 2) Photoshop has a maxInt cap on the pixel dimensions of the canvas, so if you open an Illustrator file in Photoshop, you must make sure it fits within the available pixels, otherwise Photoshop will simply constrain the canvas and distort the artwork. 3) You can open very large Illustrator files in Photoshop and use the tools there to handle issues with color profile conversions.
... View more
‎Apr 12, 2019
02:04 PM
Oh, great - Photoshop sets a 32K cap on pixels because somebody likes integer types. Can't fricking win with this stuff. I'm going to have to downscale the art, then re-import, then rescale, then resend as an Illustrator file.
... View more
‎Apr 12, 2019
01:59 PM
I did that. Curiously, both .psb and .tiff work fine, while .jpeg processing errors out. However, something funny is going on with the image aspect ratio, since the graphic, (which was generated by simply opening the .ai file in Photoshop), is now compressed horizontally by about 15%. I'm not sure if this is a Photoshop thing, since Photoshop wants to import the Illustrator file at 32000 pixels instead of the 34200 I'd expect. This does mean I now have to redo the art I just sent to the printer.
... View more
‎Apr 12, 2019
01:11 PM
As I said, cutting the resolution to 150 dpi is possible, but shouldn't be necessary. The original art is actually vector art, but was created in RGB space with overlapping transparencies and blend modes. Illustrator's colot space conversion algorithm doesn't handle this well, since it first changes the color on a per-object basis, instead of per-pixel, then re-applies the blend modes - this results in unexpected color shifts. I had no problem opening the original composition in Photoshop at 300 dpi, then converting the flattened art. Photoshop is more graceful with big files, and allows me to choose from multiple algorithms for converting the color space. Sadly, it seems that I can't bring the converted art back into Illustrator. I'm going to see if the printer will accept a flattened bitmap instead of an Illustrator file. They don't handle InDesign files.
... View more
‎Apr 12, 2019
12:53 PM
I'm trying to place a large image in the background of an Illustrator composition. The canvas is large, and the image file is 300dpi, but the file size is only 74 MB, and I'm simply trying to place it as a linked file - I should have tons of memory to spare. Nevertheless, I keep getting the message "Insufficicient Memory was Available to complete the operation". This makes no sense. Is Illustrator trying to re-rasterize the entire canvas in RAM? What's going on here? Does anyone know a workaround? I can't make the composition any smaller. (it's a 91" x 114" trade show background). Cutting the resolution is possible, but shouldn't be necessary. I have 16GB of RAM and a hefty graphics card. I'm using the latest build of Illustrator on Windows 7.
... View more
‎Apr 11, 2019
11:17 AM
3 Upvotes
Here are my responses to your questions: Issue: The operation cannot complete because of an unknown error. [!now] appears when attempting to export art to a .png. It may be because the of the desired output dimensions, but I have no way of knowing because of the ridiculous error message. This is on the latest build of Illustrator, on Windows 7. In this case I ran down the issue to canvas size by trying different file formats. Just commenting on the fact that the message is still not useful.
... View more
‎Apr 11, 2019
11:07 AM
1 Upvote
I'm experiencing the same issue in 2019. What gives? The error message is useless.
... View more
‎Oct 04, 2018
11:11 AM
Thanks very much. I am investigating with other browsers.
... View more
‎Oct 04, 2018
09:53 AM
I should have been more explicit. Naturally, I've tested with the ICM supplied by the manufacturer, and I generally leave that in place. I also tried setting everything to sRGB to see if that changed what was happening. Changing the monitor profile changes the apparent hue of all applications, but doesn't seem to impact the change in color rendering between Photoshop and Chrome. I'm starting to think that perfect color consistency is not possible, but maybe my methodology is wrong. I'm trying to select colors for web design by setting the document color space to sRGB, setting the proof mode to Internet Standard sRGB and then selecting colors from there. I have also tried monitor sRGB. When I plug those color values into an HTML document, they come out looking different - seemingly regardless of what ICM I apply to the monitor. So now I'm a little confused, and starting to doubt that I can accurately reproduce Photoshop designs in CSS. I didn't have this problem when working directly with our developers for desktop applications built in C++.
... View more
‎Oct 04, 2018
09:13 AM
By that I meant that I was working in the sRGB color space (as I wrote above), which is the default color space for Windows applications and monitors, (unless you plug in a specific ICM profile. I wanted to produce something that would be as close as possible to what the average user would see with a default set-up. There's already a lot of variation between displays, but I wanted to at least get consistent results on my own computer first. I think that there's just a variation between the way these applications render color. The shift isn't big - just annoying.
... View more
‎Oct 04, 2018
08:59 AM
Yup. That's what I said. The monitor profile was the same as the document profile in Photoshop. I set a color in Photoshop, rendered it in the browser, then got a different color back. I don't know what you mean by untagged elements. This is frustrating because I thought I was being clear in describing the problem, which is that I can't figure out how to pick a color in Photoshop, and then use CSS to render that same color in a browser. I don't know how to figure out a correct offset to account for the difference in the way Photoshop and Chrome render the same color code (say, #001265). This is happeing when I set the same profile for each. The problem is most noticeable with dark, low-saturation colors. The problem may simply be insoluble, but it's frustrating. Especially since the new fashion in web UI is dark, low saturation blues.
... View more
‎Oct 03, 2018
02:40 PM
You don't understand - the designer and I used the same color value in the same color profile, and found it rendered differently between the browser and Photoshop. We set the color value in Photoshop in sRGB IEC61966-2.1; input the value into a web layout - on the same computer, and rendered it in Chrome (supposedly in sRGB IEC61966-2.1), then picked the color generated by the browser in Photoshop - finding that it had shifted. I'm seeing color shifts on the same computer between 2 applications in the same color space, using the exact same color values. "Hex is irrelevant here. It's just a different notation for RGB - both are just random numbers unless associated with a color space." It was associated with the same color space. So the issue isn't with the proofing, but with the fact that different apps which are supposed to be in the same color space are rendering different colors. What I'm hoping is that there might be a proofing set-up that would allow me to compensate for this slight color divergence.
... View more
‎Oct 03, 2018
12:33 PM
I didn't know what a CMM was until I googled it, but the variations are small, and the direction of the variation seems to depend on the hue of the color. I imagine it's quite possible that Chrome and Photoshop use different CMMs for rendering. Is there an appropriate choice I can make in terms of the color preview settings to help me calculate color offsets? I find these variations are largest with highly saturated values, but most noticeable with low saturation colors.
... View more
‎Oct 03, 2018
12:32 PM
I see about the same rate of variation between the declared value, and the color value as read by Photoshop
... View more
‎Oct 03, 2018
11:27 AM
The monitor profile already was sRGB 2.1. That's irrelevant anyway, since I compared the output of both Photoshop and Chrome for the same hex value on the same display, and then compared the captured screenshots in Photoshop. My thinking is that Chrome may not be executing on the standard in its rendering engine. Only someone who actually knows how the Blink rendering engine works would be able to answer that. I'm wondering if there's some workaround - perhaps a profile that can be applied to the preview in Photoshop - that would allow me to select a color value in Photoshop, and derive a Hex or RGB value that would be rendered the same way in Chrome.
... View more
‎Oct 03, 2018
10:39 AM
There have been a lot of posts about images not rendering properly in browsers. My case is a little different. I have been using Photoshop to design a GUI for the web. I set the color space in Photoshop CC to sRGB IEC61966-2.1 and identified Hex values for the UI. Our web designer then created styles using these exact values, (verified with code inspector). However, when I capture the screen and examine what Chrome has rendered - the values have all shifted slightly. In general the colours read as lighter and less saturated than identical Hex values are rendered in Photoshop, using the same working and document color space. The proof setup in Photoshop is Internet Standard RGB (sRGB), though it doesn't seem to make any difference if I fiddle with that. While the monitor will display the captured graphics differently if I play with that setting, the Hex and RGB colour values detected by Photoshop don't change. For example, if I define the color #2c3741 and display it in Chrome, the resulting color is detected as #2d3741. Both applications should be color managed identically. What gives? I can't count on Internet users making any changes to the color management on their computers, so I need a good way to preview colors in Photoshop so I know how to define color values that will appear more or less the same for most people. sRGB IEC61966-2.1
... View more
‎Sep 26, 2018
09:02 AM
Dear Michelle and Barbara, That could well be. I think the confusion for me is that most conversion tables show a point as being 1.3333 pixels, which would make the 1:1 conversion factor in Photoshop just plain wrong - which is what I was getting at. However, it is possible that some browser applications render at 96 dpi, which would account for the difference I'm seeing.
... View more
‎Sep 25, 2018
04:15 PM
By the way, why is the forum server emailing me in Japanese? I don't see any language settings for this in my account...
... View more
‎Sep 25, 2018
04:07 PM
I created a design in Photoshop CC 2017 at a resolution of 72 dpi, with my units set to pixels. I also created a typography guide listing the font styles and sizes in pixels. I was asked to provide font sizes in points, but discovered that if I try changing the the units, Photoshop interprets the font sizes in points exactly the same as the size in pixels - so a font that was 15 pixels is shown as being 15 points, and a 54 pixel font is shown as being 54 points. The text blocks are lined up on a grid, and aren't being resized, so these measurements are just plain wrong. What's going on, and is there a way to fix this? At present I have no faith at all in any of the font scaling information Photoshop is giving me. When I feed these values into conversion tables the output is completely different.
... View more
Copyright © 2024 Adobe. All rights reserved.
AdChoices